Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0496

reference
159-tree-1
name
0496
tree-preservation-order

undefined

159-tpo-1
uprn
address-text
point
POINT (-1.003410 50.851887)
geometry
MULTIPOLYGON (((-1.003339 50.851879,-1.003342 50.851893,-1.003352 50.851906,-1.003367 50.851916,-1.003387 50.851922,-1.003409 50.851925,-1.003431 50.851923,-1.003451 50.851916,-1.003467 50.851907,-1.003477 50.851894,-1.003481 50.851880,-1.003478 50.851866,-1.003468 50.851854,-1.003452 50.851844,-1.003433 50.851837,-1.003411 50.851835,-1.003389 50.851837,-1.003369 50.851843,-1.003353 50.851853,-1.003343 50.851865,-1.003339 50.851879)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL